5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
- Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 2-4: Files and Fields

Files Default Process Option


The Default Input Process overlay appears on the screen when you invoke the dflt proc option from the Files/Fields screen. From this overlay, shown in the figure below, you can optionally identify the APPX input process that is used to maintain this file. Upon completion, you are returned to the Files/Fields screen.

Files Default Input Process Overlay

Default Input Process is a navigational specification that links a field on an image to the input process that optionally executes from the Scan screen.

For example, assume that a user is entering a customer number on a sales order screen. The user has forgotten the appropriate customer number, and uses the Scan option to display all of the customers and their numbers. At this point, the user discovers a problem with the customer information. If you defined a default process for the customer file, the user can elect to add a missing customer record or maintain an outdated customer record without ending the Sales Orders entry process. If you did not define a default process, the user must end Sales Orders entry, end the Sales Orders application, select the Accounts Receivable application, and select the Customer File Maintenance process to accomplish the same maintenance activity. Refer to the User Manual for a discussion of the Scan option.

Application Design Manual                                         "Powered by Appx Software"

1010

©2006 By APPX Software, Inc. All Rights Reserved